Security on Main Menu & Client View Buttons

Security is enhanced to allow authorization to add a new Policy, Client or Group Customer versus allowing a User to make and save changes to an existing record. Security can be granted on the Policy, Client or GroupCustomer pages for the ‘New’ button and/or the ‘Save’ button. If a Security Group has access to the ‘New’ button they will automatically be granted access to the ‘Save’ button. If the Security Group does not have access to the applicable ‘New’ button they will not see the Main Menu sub menu option of ‘New’ under the Policy, Client, or Group Customer menus. If the User does not have access to the ‘Save’ button, the ‘Save’ button will not be visible on the applicable screen.

 

Prototype Configuration Detail PrerequisitesThe following are the security user considered for showcasing of prototype scenarios:

Prototype Super

Prototype Tester

Prototype Analyst

 

Existing Items ‘Prototype Super’ Security Group:

'Policy' Plan Page:

1. Add New - 'Policy' Plan Page:

Security for 'New' button is present by default for the entire plans of the below companies:

Prototype Group Child Company

Prototype Individual Child Company

Policy' plan page: Admin Explorer > Security > Application Security > Security Groups > Prototype Super > Plan Security > Prototype Individual Child Company > Dynamic Prototype Plan > Plan Pages > Policy

Once security for 'New' button is granted security for 'Save' button is also granted.

Result: In OIPA when the user associated to ‘Prototype Super’ security logs in then the 'New' sub menu option under 'Policy' main menu is shown and also user is able to 'Save' the existing/new policy content.

 

2. Add New - 'Client' Company Page:

Security for 'New' button is present by default in ‘Client’ Company page which is in the path as mention below:

Admin Explorer > Security > Application Security > Security Groups > Prototype Super > Company Security > Company Pages > Prototype > Client

Once Security for 'New' button is granted security for 'Save' button is also granted.

Result: In OIPA, when user associated to ‘Prototype Super’ security group is logged in then the 'New' sub menu option under 'Client' main menu is shown and also user is able to 'Save' the existing/new client content.

 

3. Add New - 'GroupCustomer' Company Page:

Security for 'New' button is present by default in 'GroupCustomer' Company page which is in the path as mention below:

Admin Explorer > Security > Application Security > Security Groups > Prototype Super > Company Security > Company Pages > Prototype > GroupCustomer.

Once 'New' button is granted security for 'Save' button is also granted.

Result: In OIPA, when user associated to ‘Prototype Super’ security is logged in then the 'New' sub menu option under 'Group Customer' main menu is shown and also user is able to 'Save' the existing/new Group Customer

content.

 

‘Prototype Tester’ Security user:

1. Save only - 'Policy' Plan Page: Security is removed for 'New' button and security to 'Save' button is given in the 'Policy' Plan Page of Functional Prototype Plan which is in the path as mention below:Admin Explorer > Security > Application Security > Security Groups > Prototype Tester > Plan Security > Prototype Individual Child company > Functional Prototype Plan > Plan Pages > Policy

Result: In OIPA, when the user associated to ‘Prototype Tester’ is logged in, the 'New' sub menu option under 'Policy' main menu is not shown. The user is able to 'Save' the existing Policy content of Functional Prototype Plan policy.

 

2. Save only - 'Client' Company Page:

Security is removed for 'New' button and security to 'Save' button is given in the ‘Client’ Company page which is in the path as mention below:

Admin Explorer > Security > Application Security > Security Groups > Prototype Tester > Company Security > Company Pages > Prototype > Client

Result: In OIPA, when the user associated to ‘Prototype Tester’ security is logged in, the 'New' sub menu option under 'Client' main menu is not shown. The user is able to 'Save' an existing Client contents.

 

3. Save only - 'Group Customer' Company Page

Security is removed for 'New' button and security to 'Save' button is given in the 'Group Customer' Company page which is in the path as mention below:

Admin Explorer > Security > Application Security > Security Groups > Prototype Tester > Company Security > Company Pages > Prototype > Group Customer.

Result: In OIPA, when the user associated to ‘Prototype Tester’ security is logged in, the 'New' sub menu option under 'Group Customer' main menu is not shown. The user is able to 'Save' an existing Group Customer contents.

 

‘Prototype Analyst’ Security user:

1. No New or Save - 'Policy' Plan Page:

Security is removed for both 'New' and 'Save' buttons in the 'Policy' Plan Page of the Dynamic Prototype Plan which is in the path as mention below:

Admin Explorer > Security > Application Security > Security Groups > Prototype Analyst > Plan Security > Prototype Individual Child company > Dynamic Prototype Plan > Plan Pages > Policy

Result: In OIPA, when the user associated to ‘Prototype Analyst’ security is logged in, the 'New' sub menu option under 'Policy' main menu is not shown. The 'Save' button is not available for the existing Dynamic Prototype Plan Policies.

 

2. No New or Save - 'Client' Company Page:

Security is removed for both 'New' and 'Save' buttons in the ‘Client’ Company page which is in the path as mention below:

Admin Explorer > Security > Application Security > Security Groups > Prototype Analyst > Company Security > Company Pages > Prototype > Client

Result: In OIPA, when the user associated to ‘Prototype Analyst’ security is logged in, the 'New' sub menu option under 'Client' main menu is not shown. The 'Save' button is not available for an existing Client.

 

3. No New or Save - 'Group Customer' Company Page:

Security is removed for both 'New' and 'Save' buttons in the 'GroupCustomer' Company page which is in the as mention below:

Admin Explorer > Security > Application Security > Security Groups > Prototype Analyst > Company Security > Company Pages > Prototype > Group Customer.

Result: In OIPA, when the user associated to ‘Prototype Analyst’ security is logged in, the 'New' sub menu option under 'Group Customer' main menu is not shown. The 'Save' button is not available for an existing Group Customer.

Security for Add WorkFlow Task Button

OIPA supports security configuration for the Add Workflow Task button displayed in the left navigation of supported entity screens. This allows administrators to control which security groups can create workflow tasks from the OIPA user interface.

The button is controlled by both:

  1. The workflow.enabled property in pas.properties.

  2. The AddWorkflowTask security check box in Rules Palette.

Both settings must allow access for the workflow button to be visible and usable.

Prerequisite

workflow.enabled=Yes

Note: If workflow.enabled=No, workflow functionality is hidden in OIPA regardless of security group configuration.

Security Button

A new security button named `AddWorkflowTask` is available for supported screens. By default, this security option is not selected.

When selected for a security group, the OIPA user in that group can view and use the **Add Workflow Task** button, provided workflow is enabled in pas.properties.

Supported Screens and Security Paths

| OIPA Screen | Rules Palette Security Path |

|---|---|

| Client Screen | Security Groups > [SecurityGroupName] > Company Security > Company Pages > [Company Name] > Client > AddWorkflowTask` |

| Group Customer Screen | `Security Groups > [SecurityGroupName] > Company Security > Company Pages > [Company Name] > GroupCustomer > AddWorkflowTask` |

| Policy Screen | Security Groups > [SecurityGroupName] > Plan Security > [Company Name] > [Product Name] > Plan Pages > Policy > AddWorkflowTask |

| Application Screen | Uses the same AddWorkflowTask security setting as the Policy Screen |

Application Screen Behavior

The Application screen does not have a separate `AddWorkflowTask` security setting. The **Add Workflow Task** button on the Application screen is controlled by the Policy screen security configuration because Application left navigation security is loaded from Policy security.

Expected Behavior

| workflow.enabled | AddWorkflowTask Security | Result |

|---|---|---|

| Yes | Enabled| Workflow functionality is visible, and the user can access the **Add Workflow Task** button. |

| Yes | Disabled| Workflow functionality is available, but the **Add Workflow Task** button is hidden for the user. |

| No | Selected | Workflow functionality and the **Add Workflow Task** button are hidden. The property setting takes precedence. |

| No | Not selected | Workflow functionality and the **Add Workflow Task** button are hidden. |

Version Notes

The Add Workflow Task button is available on the following screens:

  • Client Screen

  • Policy Screen

  • Application Screen

  • Group Customer Screen

Configuration Notes

  • Existing workflow behavior remains unchanged unless AddWorkflowTask security is configured.

  • Users must belong to a security group where AddWorkflowTask is enabled for the applicable screen.

  • If the security check box is not selected, the button is hidden even when workflow is enabled.

  • The workflow.enabled property controls overall workflow availability and takes precedence over Rules Palette security.